Is it possible for anyone to give Microsoft a fair trial? The first half of 2012 is in the history books. Yet the firm still cannot seem to shake the public opinion as The Evil Empire that produces crap code.

I am in a unique position. I joined the orbit of Microsoft in 1973 after the Army decided it didn't need photographers flying around in helicopters in Vietnam anymore. I was sent to Fort Lewis and assigned to 9th Finance because I had a smattering of knowledge about computers. And the Army was going to a computerized payroll system.

Bill and Paul used the University of Washington's VAX PDP computer to create BASIC for the Altair computer. Certainly laughable by today's standards, it is the very roots of the home computer.

Microsoft became successful because it delivered what people wanted.

I will begin our blog on Java Tutorial with an incredibly important aspect of java development:  memory management.  The importance of this topic should not be minimized as an application's performance and footprint size are at stake.

From the outset, the Java Virtual Machine (JVM) manages memory via a mechanism known as Garbage Collection (GC).  The Garbage collector

• Manages the heap memory.   All obects are stored on the heap; therefore, all objects are managed.  The keyword, new, allocates the requisite memory to instantiate an object and places the newly allocated memory on the heap.  This object is marked as live until it is no longer being reference.
• Deallocates or reclaims those objects that are no longer being referened. 
• Traditionally, employs a Mark and Sweep algorithm.  In the mark phase, the collector identifies which objects are still alive.  The sweep phase identifies objects that are no longer alive.
• Deallocates the memory of objects that are not marked as live.
• Is automatically run by the JVM and not explicitely called by the Java developer.  Unlike languages such as C++, the Java developer has no explict control over memory management.
• Does not manage the stack.  Local primitive types and local object references are not managed by the GC.

So if the Java developer has no control over memory management, why even worry about the GC?  It turns out that memory management is an integral part of an application's performance, all things being equal.  The more memory that is required for the application to run, the greater the likelihood that computational efficiency suffers. To that end, the developer has to take into account the amount of memory being allocated when writing code.  This translates into the amount of heap memory being consumed.

Memory is split into two types:  stack and heap.  Stack memory is memory set aside for a thread of execution e.g. a function.  When a function is called, a block of memory is reserved for those variables local to the function, provided that they are either a type of Java primitive or an object reference.  Upon runtime completion of the function call, the reserved memory block is now available for the next thread of execution.  Heap memory, on the otherhand, is dynamically allocated.  That is, there is no set pattern for allocating or deallocating this memory.  Therefore, keeping track or managing this type of memory is a complicated process. In Java, such memory is allocated when instantiating an object:

String s = new String();  // new operator being employed
String m = "A String";    /* object instantiated by the JVM and then being set to a value.  The JVM
calls the new operator */

The future looks just as bright for information technology as it did ten years ago when this career field started growing in huge numbers due to major internet technological advances and the popularity of mobile devices such as the smartphone and eReaders like Amazon’s Kindle.  In classrooms and libraries across the nation, information technology has become instrumental in the way students learn and the way teachers give lessons, and thanks to online education more adults have access to a better education without incurring a lot of debt. Needles to say, the need for qualified workers in information technology will continue in times to come. Some of the technological careers that are rapidly growing in popularity in the last decade are a direct reflection of current trends.

Information Technology Managers

The information technology manager is responsible for handling all computer activities for a business and performs upgrades on computer software and hardware, installs new security features on computers, creates budgets and goals for the IT department, supervises other IT employees and troubleshoots computers when needed. According to the Bureau of Labor Statistics, there were 332,700 information technology management jobs filled in 2012 and a majority of these positions were in the computer systems sector. Most information technology managers hold a bachelor's degree in computer science or information technology, and a growing number of employers prefer a graduate degree. The job growth is expected to grow at 15% between now and 2022.

Mobile Application Developers

This job will grow by leaps and bounds as millions of people continue to purchase mobile devices and download apps for business and entertainment purposes. It creates expanded opportunities for those who want to become mobile application developers. A mobile application developer often works with other developers to create mobile-friendly apps or mobile-friendly versions of business websites for consumers. The developer may have his own firm or he may be employed with a larger company, and he will need to understand the basics of web design and different kinds of codes to succeed in this career. The Bureau of Labor Statistics states that the job growth is expected to be at 28% by 2020.

Health Information Technology

Another fast growing sector within information technology is health information technology and there are various jobs to choose from. You can work with health insurance providers and your duties would include processing patients' insurance claims and managing patients' insurance information using a computer database. Another option is to work as a medical biller in a doctor's office preparing patient’s invoices. The good thing about these jobs is that you do not need a four-year degree to get the training; you can obtain a two-year associates degree or a certificate in health information technology.

Search Engine Optimization Consultant

This is an important information technology career because most businesses have websites and if these websites are going to receive high traffic from visitors and earn profit, proper search engine optimization is necessary. The SEO consultant's job is to ensure that a business website gets high rankings on the major search engines and plenty of traffic from visitors. A good SEO consultant at a minimum will know how to research keywords effectively and implement these into the website's content based on the website's theme and he would utilize web analytics as part of the job. An SEO consultant may work on a freelance basis or be employed with an advertising company as an example.

Best Cities for Technology Careers

If you're thinking about relocating for your career, here are some of the best cities currently for information technology jobs listed in Forbes. 

Millions of people experienced the frustration and failures of the Obamacare website when it first launched. Because the code for the back end is not open source, the exact technicalities of the initial failings are tricky to determine. Many curious programmers and web designers have had time to examine the open source coding on the front end, however, leading to reasonable conclusions about the nature of the overall difficulties.

Lack of End to End Collaboration
The website was developed with multiple contractors for the front-end and back-end functions. The site also needed to be integrated with insurance companies, IRS servers, Homeland Security servers, and the Department of Veterans Affairs, all of whom had their own legacy systems. The large number of parties involved and the complex nature of the various components naturally complicated the testing and integration of each portion of the project.

The errors displayed, and occasionally the lack thereof, indicated an absence of coordination between the parties developing the separate components. A failed sign up attempt, for instance, often resulted in a page that displayed the header but had no content or failure message. A look at end user requests revealed that the database was unavailable. Clearly, the coding for the front end did not include errors for failures on the back end.

Bloat and the Abundance of Minor Issues
Obviously, numerous bugs were also an issue. The system required users to create passwords that included numbers, for example, but failed to disclose that on the form and in subsequent failure messages, leaving users baffled. In another issue, one of the pages intended to ask users to please wait or call instead, but the message and the phone information were accidentally commented out in the code.

While the front-end design has been cleared of blame for the most serious failures, bloat in the code did contribute to the early difficulties users experienced. The site design was heavy with Javascript and CSS files, and it was peppered with small coding errors that became particularly troublesome when users faced bottlenecks in traffic. Frequent typos throughout the code proved to be an additional embarrassment and were another indication of a troubled development process.

NoSQL Database
The NoSQL database is intended to allow for scalability and flexibility in the architecture of projects that will use it. This made NoSQL a logical choice for the health insurance exchange website. The newness of the technology, however, means personnel with expertise can be elusive. Database-related missteps were more likely the result of a lack of experienced administrators than with the technology itself. The choice of the NoSQL database was thus another complication in the development, but did not itself cause the failures.

Another factor of consequence is that the website was built with both agile and waterfall methodology elements. With agile methods for the front end and the waterfall methodology for the back end, streamlining was naturally going to suffer further difficulties. The disparate contractors, varied methods of software development, and an unrealistically short project time line all contributed to the coding failures of the website.